5. Part II — Task Tests
The following set of tests verifies that basic mobile task management can be accomplished. In particular they attempt to verify the following:
that Tasks can be created, modified, and deleted on the device or server
that Task Access Levels and Priorities can be correctly mapped
that Task reminders can be correctly mapped
that Tasks can be marked as completed and have this fact reflected on either side
that special characters and multi byte characters can be correctly handled
Test ID | Objective | Procedure | Expected Result |
|---|---|---|---|
6.1 Create task | Verify that basic task information can be synchronized | Create a task on the server Complete all fields with maximum input. Perform a synchronization Modify the task on the device. Perform a synchronization Modify the task on the server Perform a synchronization | The task should be synchronized to the device with server fields correctly mapped to the corresponding supported fields on the device. After second synchronization device modification should be propagated to the server. Any truncation that occurred device side should not affect the server. After third synchronization server modification should be reflected on the device. |
6.2 Task Access Level and Priority | Verify that access level and priority values in tasks correctly synchronize to the device. Verify that any form of mapping that occurs does not have adverse effects | From the Server, create a task with default access and priority (e.g. Normal/Medium). Perform a synchronization From the device, modify the event. Perform a synchronization Repeat making sure to test all supported access level and priorities. | The task should display on the device with the access level and priority appropriately mapped if needed. After making modifications and synchronizing, the changes should display on the server as well. There should be no evidence of any change server-side to the access level or priority if not actually part of the modification done |
6.3 Create task with alarm | Verify that task reminders can be synchronized | Create a task on the server Complete title, due date, priority, and access/privacy fields. Set category for task (if supported) Set an alarm reminder for both the start date and the due date. Perform a synchronization | The task should be synchronized to the device with all fields correctly mapped to the corresponding fields on the device. An appropriate mapping of the server side reminders should be present on the devices. |
6.4 Mark task as completed | Verify that task completion can be synchronized | Create a task on the server Complete title, due date, priority and access/privacy fields Perform a synchronization Set task as complete on server Perform a synchronization | The task should be synchronized to the device, with all fields correctly mapped. After second synchronization, task should be marked as complete on the device |
6.5 Special Characters From Server | Verify that special characters in tasks correctly synchronize to the device. | From the Server, create a task filling out all fields with special characters. Perform a synchronization From the device, modify the task. Perform a synchronization | The task should display on the device with all fields on the server correctly mapped to corresponding fields on the device. All special characters should correctly display on the device as it is displayed on the server. After modifying the task, the characters should remain correctly displayed on both the device and server and the changes made on the device should be reflected on the server |
6.6 Multi-Byte Characters From Server | Verify that multi-byte characters in tasks correctly synchronize to the device. | From the server, create a task filling out all fields with multi-byte characters. Perform a synchronization From the device modify the event. Perform a synchronization | The task should display on the device with all multi-byte characters correctly displayed. After modifying the task, the multi-byte characters should remain correctly displayed on both the device and server, and the changes made on the device should be reflected on the server. |
6.7 Deletion | Verify that tasks deleted server side are deleted on the device | From the server delete all tasks created in previous tests. Perform a synchronization | The deleted tasks should be deleted off of the device as well. |
Test ID | Objective | Procedure | Expected Result |
|---|---|---|---|
6.8 Create task | Verify that basic task information can be synchronized | Create a task on the device Complete all fields with maximum input. Perform a synchronization Modify the task on the device Perform a synchronization | The task should be synchronized to the server with fields correctly mapped to the corresponding supported fields on the server. After second synchronization device modification should be reflected on the server. |
6.9 Task Access Level and Priority | Verify that access level and priority values in tasks correctly synchronize to the server. | From the device, create a task with default access and priority (e.g. Normal/Medium). Perform a synchronization Repeat making sure to test all supported access level and priorities. | The task should display on the server with the access level and priority appropriately mapped if needed. |
6.10 Create task with alarm | Verify that task reminders can be synchronized | Create a task on the device Set an alarm reminder (as allowed by the device). Perform a synchronization | The task should be synchronized to the device with all fields correctly mapped to the corresponding fields on the device. An appropriate mapping of the device side reminder(s) should be present on the server. |
6.11 Mark task as completed | Verify that task completion can be synchronized | Create a task on the device Complete title, due date, priority and access/privacy fields Perform a synchronization Set task as complete on device Perform a synchronization | The task should be synchronized to the server, with all fields correctly mapped. After second synchronization, task should be marked as complete on the server |
6.12 Special Characters From Device | Verify that special characters in tasks correctly synchronize to the server. | From the device, create a task filling out all fields with special characters. Perform a synchronization From the server, modify the task. Perform a synchronization | The task should display on the server with all fields on the device correctly mapped to corresponding fields on the server. All special characters should correctly display on the server as it is displayed on the device. After modifying the task, the characters should remain correctly displayed on both the device and server and the changes made on the server should be reflected on the device |
6.13 Multi-Byte Characters From Device | Verify that multi-byte characters in tasks correctly synchronize to the server. | From the device, create a task filling out all fields with multi-byte characters. Perform a synchronization From the server modify the event. Perform a synchronization | The task should display on the server with all multi-byte characters correctly displayed. After modifying the task, the multi-byte characters should remain correctly displayed on both the device and server, and the changes made on the server should be reflected on the device. |
6.14 Deletion | Verify that tasks deleted device side are deleted on the device | From the device delete all tasks created in previous tests. Perform a synchronization | The deleted tasks should be deleted off of the server as well. |